General requirements for importing data

For more information, see the KB article PowerMax File: Errors are encountered during the Source NAS Server's discovery process.

  • Following protocols on source sites are supported
    • SMB - SMB1/SMB3 Note - SMB1 has security vulnerability.
    • NFS - NFSv2, NFSv3
  • No UI support to trigger preparation of source eNAS 1.0 box for migration.
  • Support only Unified ENAS/eNAS as a migration source array, starting from version 8.1.15.401 for eNAS/All-Flash VMAX and 8.1.15.601 for eNAS/Hybrid VMAX
  • Need to allocate an IP address for the target import interface per VDM/DM migration.
  • VDM/DM containing multiple SMB servers cannot be migrated.
  • SMB1 protocol must be enabled on the source to migrate an SMB server.
  • VDM/DM with the NFSv4 protocol enabled is not supported in current release.
    NOTE:  No NFS ACL migration
  • VDM/DM with Secure NFS or pNFS configured is not supported for migration.
  • Migration of replications sessions (IP or VDM SYNC) (although replication can be running during the migration) not supported.
  • Migration of checkpoint/snapshot or checkpoint/snapshot schedule not supported.
  • eNAS/Filesystem level compressed files are uncompressed during the migration.
  • No transparency on cutover for SMB.
  • VDM/DM with custom international characters translation (XLT.cfg) cannot be imported.
  • DHSM server must be enabled on the source w/o SSL persona if there is an FLR FS to be imported is not supported.
  • Filesystem:
    • VDM/DM having a Nested Mount File System (NMFS) cannot be migrated
    • Cannot migrate filesystem that is a replication destination
    • Cannot migrate filesystem whose mount path contains more than 2 slashes
  • Cannot migrate filesystem with FLR auto-lock or auto-delete feature enabled.
  • Rollback limitations:
    • Rollback may be disruptive (NFSv3 clients also must remount)
    • Rollback of the configuration to the source is very limited
  • Do NOT migrate:
    • FTP/SFTP (File Transfer Protocol)
    • HTTP (Hyper Text Transfer Protocol)
    • CEPP (Celerra Event Publishing)
    • CAVA settings
    • DHSM connections
    • CA (Continuous Availability)
  • Source configuration can be changed by the user causing the import to fail.
  • Imported external services (DNS, NIS, LDAP, AD DC) must be available and respond to ICMP pings from VDM/DM production interfaces being imported - to be accessible on the target after cutover
  • All DM external services (DNS, NIS, LDAP, AD DC, CAVA, Usermapper) must be available and respond to ICMP pings from any DM interface which is NOT being imported (including the import source interface and interfaces of other VDMs) - to remain accessible on the source after cutover.
  • The automatic precheck may miss issues if there are concurrent imports
  • Requirements on the default network route:
  • In the subnet of the default gateway there must be at least one production interface which will be imported OR the gateway must be overridden on the target by the user
  • In the subnet of the default gateway there must be at least one interface on the source which will NOT be imported (the source import interface or any interface of another VDM or an interface not attached to CIFS server in case of SMB import)
  • Neither VDM, nor DM can be imported if there is a network interface attached to VDM CIFS server, but not attached to VDM NFS server, thus exporting VDM and DM FS data at the same time.
  • Neither VDM, nor DM can be imported if any data from VDM-mounted FS is exported though DM via NFS, SMB (expect C$ which is unavoidable), FTP.
  • DM cannot be imported if FTP service is enabled.

Datamover mounted filesystem are supported for migration. Datamover at times is referred as default VDM.